Method for a configuration error management for a sidelink radio bearer and device therefor

ABSTRACT

The present invention relates to a wireless communication system. More specifically, the present invention relates to a method and a device for a configuration error management for a sidelink radio bearer, the method comprising detecting configuration error for a sidelink radio bearer comprising a RLC entity and a PDCP entity, starting a timer when the configuration error for the sidelink radio bearer is detected, generating a configuration error recovery request including an identifier of the sidelink radio bearer, and transmitting the configuration error recovery request to a network or a peer UE directly connected to the UE via a sidelink.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is the National Phase of PCT International ApplicationNo. PCT/KR2015/003964, filed on Apr. 21, 2015, which claims priorityunder 35 U.S.C. 119(e) to U.S. Provisional Application No. 61/984,047,filed on Apr. 25, 2014, all of which are hereby expressly incorporatedby reference into the present application.

TECHNICAL FIELD

The present invention relates to a wireless communication system and,more particularly, to a method for a configuration error management fora sidelink radio bearer and a device therefor.

BACKGROUND ART

As an example of a mobile communication system to which the presentinvention is applicable, a 3rd Generation Partnership Project Long TermEvolution (hereinafter, referred to as LTE) communication system isdescribed in brief.

FIG. 1 is a view schematically illustrating a network structure of anE-UMTS as an exemplary radio communication system. An Evolved UniversalMobile Telecommunications System (E-UMTS) is an advanced version of aconventional Universal Mobile Telecommunications System (UMTS) and basicstandardization thereof is currently underway in the 3GPP. E-UMTS may begenerally referred to as a Long Term Evolution (LTE) system. For detailsof the technical specifications of the UMTS and E-UMTS, reference can bemade to Release 7 and Release 8 of “3rd Generation Partnership Project;Technical Specification Group Radio Access Network”.

Referring to FIG. 1, the E-UMTS includes a User Equipment (UE), eNode Bs(eNBs), and an Access Gateway (AG) which is located at an end of thenetwork (E-UTRAN) and connected to an external network. The eNBs maysimultaneously transmit multiple data streams for a broadcast service, amulticast service, and/or a unicast service.

One or more cells may exist per eNB. The cell is set to operate in oneof bandwidths such as 1.25, 2.5, 5, 10, 15, and 20 MHz and provides adownlink (DL) or uplink (UL) transmission service to a plurality of UEsin the bandwidth. Different cells may be set to provide differentbandwidths. The eNB controls data transmission or reception to and froma plurality of UEs. The eNB transmits DL scheduling information of DLdata to a corresponding UE so as to inform the UE of a time/frequencydomain in which the DL data is supposed to be transmitted, coding, adata size, and hybrid automatic repeat and request (HARQ)-relatedinformation. In addition, the eNB transmits UL scheduling information ofUL data to a corresponding UE so as to inform the UE of a time/frequencydomain which may be used by the UE, coding, a data size, andHARQ-related information. An interface for transmitting user traffic orcontrol traffic may be used between eNBs. A core network (CN) mayinclude the AG and a network node or the like for user registration ofUEs. The AG manages the mobility of a UE on a tracking area (TA) basis.One TA includes a plurality of cells.

Device to device (D2D) communication refers to the distributedcommunication technology that directly transfers traffic betweenadjacent nodes without using infrastructure such as a base station. In aD2D communication environment, each node such as a portable terminaldiscovers user equipment physically adjacent thereto and transmitstraffic after setting communication session. In this way, since D2Dcommunication may solve traffic overload by distributing trafficconcentrated into the base station, the D2D communication may havereceived attention as the element technology of the next generationmobile communication technology after 4G. For this reason, the standardinstitute such as 3GPP or IEEE has proceeded to establish the D2Dcommunication standard on the basis of LTE-A or Wi-Fi, and Qualcomm hasdeveloped their own D2D communication technology.

It is expected that the D2D communication contributes to increasethroughput of a mobile communication system and create new communicationservices. Also, the D2D communication may support proximity based socialnetwork services or network game services. The problem of link of a userequipment located at a shade zone may be solved by using a D2D link as arelay. In this way, it is expected that the D2D technology will providenew services in various fields.

The D2D communication technologies such as infrared communication,ZigBee, radio frequency identification (RFID) and near fieldcommunications (NFC) based on the RFID have been already used. However,since these technologies support communication only of a specific objectwithin a limited distance (about 1 m), it is difficult for thetechnologies to be regarded as the D2D communication technologiesstrictly.

Although the D2D communication has been described as above, details of amethod for transmitting data from a plurality of D2D user equipmentswith the same resource have not been suggested.

DISCLOSURE Technical Problem

An object of the present invention devised to solve the problem lies ina method and device for a configuration error management for a sidelinkradio bearer. The technical problems solved by the present invention arenot limited to the above technical problems and those skilled in the artmay understand other technical problems from the following description.

Technical Solution

The object of the present invention can be achieved by providing amethod for a User Equipment (UE) operating in a wireless communicationsystem, the method comprising: detecting configuration error for asidelink radio bearer comprising a RLC (Radio Link Control) entity and aPDCP (Packet Data Convergence Protocol) entity; starting a timer whenthe configuration error for the sidelink radio bearer is detected;generating a configuration error recovery request including anidentifier of the sidelink radio bearer; and transmitting theconfiguration error recovery request to a network or a peer UE directlyconnected to the UE via a sidelink.

Preferably, the identifier of the sidelink radio bearer includes atleast one of a SourceID, a TargetID or a LCID (Logical Channel ID).

Preferably, the configuration error recovery request further compriseslayer information of the detected configuration error, or typeinformation of the detected configuration error.

Preferably, the type information of the detected configuration errorincludes at least one header decompression, reception of a PDCP PDU(Protocol Data Unit) containing reserved or invalid values, or receptionof a RLC PDU containing reserved or invalid values.

Preferably, the method further comprises: receiving configurationinformation in response to the configuration error recovery request fromthe peer UE or the network while the timer is running; stopping thetimer when the configuration information is received; andre-establishing the RLC and the PDCP entities for the sidelink radiobearer according to the configuration information.

Preferably, the configuration information includes at least one ofPDCP-SN-Size, headerCompression, SN-FieldLength, and T-Reordering.

Preferably, the method further comprises: transmitting recovery failindicator to the network or to the peer UE when the timer expires.

Preferably, the recovery fail indicator includes an identifier of thesidelink radio bearer including at least one of a SourceID, a TargetIDor a LCID (Logical Channel ID).

Preferably, the method further comprises: releasing the RLC and the PDCPentities of the sidelink radio bearer after the recovery fail indicatoris transmitted.

Preferably, a value of the timer is received from a network or the peerUE as form of at least one of RRC (Radio Resource Control), PDCP (PacketData Convergence Protocol), RLC (Radio Link Control), MAC (Medium AccessControl), or PHY (PHYsical) signal, or the value of the timer ispredefined.

Preferably, the timer is configured per a sidelink radio bearer, whereina value of the timer has independent value used for each timer, orwherein a value of the timer has common value used for all timers.

Preferably, the configuration error for the sidelink radio bearer isdetected if a number of erroneous D2D (Device to Device) packets isequal to or larger than a threshold, the erroneous D2D packets arecounted among one or more D2D packets received via a sidelink radiobearer.

Preferably, the UE counts only consecutive erroneous D2D packets whenthe erroneous D2D packets are counted.

Preferably, the counted erroneous D2D packets are received consecutivelyif the configuration error is detected.

Preferably, the counted erroneous D2D packets are received within apredefined time period.

Preferably, the one or more D2D packets are counted as the erroneous D2Dpackets in one of following cases: i) when header decompression failureoccurs in a PDCP entity of the sidelink radio bearer, ii) when a PDCPPDU (Protocol Data Unit) that contains reserved or invalid values isreceived in the PDCP entity of the sidelink radio bearer, or iii) when aRLC PDU that contains reserved or invalid values is received in a RLCentity of the sidelink radio bearer.

It is to be understood that both the foregoing general description andthe following detailed description of the present invention areexemplary and explanatory and are intended to provide furtherexplanation of the invention as claimed.

Advantageous Effects

According to the present invention, a configuration error for a sidelinkradio bearer can be efficiently managed in D2D communication system. Itwill be appreciated by persons skilled in the art that that the effectsachieved by the present invention are not limited to what has beenparticularly described hereinabove and other advantages of the presentinvention will be more clearly understood from the following detaileddescription taken in conjunction with the accompanying drawings.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention.

FIG. 1 is a diagram showing a network structure of an Evolved UniversalMobile Telecommunications System (E-UMTS) as an example of a wirelesscommunication system;

FIG. 2A is a block diagram illustrating network structure of an evolveduniversal mobile telecommunication system (E-UMTS), and FIG. 2B is ablock diagram depicting architecture of a typical E-UTRAN and a typicalEPC;

FIG. 3 is a diagram showing a control plane and a user plane of a radiointerface protocol between a UE and an E-UTRAN based on a 3rd generationpartnership project (3GPP) radio access network standard;

FIG. 4 is a diagram of an example physical channel structure used in anE-UMTS system;

FIG. 5 is a block diagram of a communication apparatus according to anembodiment of the present invention;

FIG. 6 is an example of default data path for a normal communication;

FIGS. 7˜8 are examples of data path scenarios for a proximitycommunication;

FIG. 9 is a conceptual diagram illustrating for a non-roaming referencearchitecture;

FIG. 10 is a conceptual diagram illustrating for a Layer 2 Structure forSidelink;

FIG. 11a is a conceptual diagram illustrating for User-Plane protocolstack for ProSe Direct Communication, and FIG. 11b is Control-Planeprotocol stack for ProSe Direct Communication;

FIG. 12 is a conceptual diagram illustrating for a PC5 interface forProSe Direct Discovery;

FIG. 13 is a conceptual diagram illustrating for overview model of theRLC sub layer;

FIG. 14 is a conceptual diagram illustrating for model of twounacknowledged mode peer entities;

FIGS. 15a to 15f are conceptual diagrams illustrating for UMD PDU;

FIG. 16 is a conceptual diagram for functional view of a PDCP entity;

FIG. 17 is a conceptual diagram for transmitting aRadioResourceConfigDedicated from E-UTRAN to a UE; and

FIGS. 18-21 are conceptual diagrams for a configuration error managementfor a sidelink radio bearer according to embodiments of the presentinvention.

BEST MODE

Universal mobile telecommunications system (UMTS) is a 3rd Generation(3G) asynchronous mobile communication system operating in wideband codedivision multiple access (WCDMA) based on European systems, globalsystem for mobile communications (GSM) and general packet radio services(GPRS). The long-term evolution (LTE) of UMTS is under discussion by the3rd generation partnership project (3GPP) that standardized UMTS.

The 3GPP LTE is a technology for enabling high-speed packetcommunications. Many schemes have been proposed for the LTE objectiveincluding those that aim to reduce user and provider costs, improveservice quality, and expand and improve coverage and system capacity.The 3G LTE requires reduced cost per bit, increased serviceavailability, flexible use of a frequency band, a simple structure, anopen interface, and adequate power consumption of a terminal as anupper-level requirement.

Hereinafter, structures, operations, and other features of the presentinvention will be readily understood from the embodiments of the presentinvention, examples of which are illustrated in the accompanyingdrawings. Embodiments described later are examples in which technicalfeatures of the present invention are applied to a 3GPP system.

Although the embodiments of the present invention are described using along term evolution (LTE) system and a LTE-advanced (LTE-A) system inthe present specification, they are purely exemplary. Therefore, theembodiments of the present invention are applicable to any othercommunication system corresponding to the above definition. In addition,although the embodiments of the present invention are described based ona frequency division duplex (FDD) scheme in the present specification,the embodiments of the present invention may be easily modified andapplied to a half-duplex FDD (H-FDD) scheme or a time division duplex(TDD) scheme.

FIG. 2A is a block diagram illustrating network structure of an evolveduniversal mobile telecommunication system (E-UMTS). The E-UMTS may bealso referred to as an LTE system. The communication network is widelydeployed to provide a variety of communication services such as voice(VoIP) through IMS and packet data.

As illustrated in FIG. 2A, the E-UMTS network includes an evolved UMTSterrestrial radio access network (E-UTRAN), an Evolved Packet Core (EPC)and one or more user equipment. The E-UTRAN may include one or moreevolved NodeB (eNodeB) 20, and a plurality of user equipment (UE) 10 maybe located in one cell. One or more E-UTRAN mobility management entity(MME)/system architecture evolution (SAE) gateways 30 may be positionedat the end of the network and connected to an external network.

As used herein, “downlink” refers to communication from eNodeB 20 to UE10, and “uplink” refers to communication from the UE to an eNodeB. UE 10refers to communication equipment carried by a user and may be alsoreferred to as a mobile station (MS), a user terminal (UT), a subscriberstation (SS) or a wireless device.

FIG. 2B is a block diagram depicting architecture of a typical E-UTRANand a typical EPC.

As illustrated in FIG. 2B, an eNodeB 20 provides end points of a userplane and a control plane to the UE 10. MME/SAE gateway 30 provides anend point of a session and mobility management function for UE 10. TheeNodeB and MME/SAE gateway may be connected via an S1 interface.

The eNodeB 20 is generally a fixed station that communicates with a UE10, and may also be referred to as a base station (BS) or an accesspoint. One eNodeB 20 may be deployed per cell. An interface fortransmitting user traffic or control traffic may be used between eNodeBs20.

The MME provides various functions including NAS signaling to eNodeBs20, NAS signaling security, AS Security control, Inter CN node signalingfor mobility between 3GPP access networks, Idle mode UE Reachability(including control and execution of paging retransmission), TrackingArea list management (for UE in idle and active mode), PDN GW andServing GW selection, MME selection for handovers with MME change, SGSNselection for handovers to 2G or 3G 3GPP access networks, Roaming,Authentication, Bearer management functions including dedicated bearerestablishment, Support for PWS (which includes ETWS and CMAS) messagetransmission. The SAE gateway host provides assorted functions includingPer-user based packet filtering (by e.g. deep packet inspection), LawfulInterception, UE IP address allocation, Transport level packet markingin the downlink, UL and DL service level charging, gating and rateenforcement, DL rate enforcement based on APN-AMBR. For clarity MME/SAEgateway 30 will be referred to herein simply as a “gateway,” but it isunderstood that this entity includes both an MME and an SAE gateway.

A plurality of nodes may be connected between eNodeB 20 and gateway 30via the S1 interface. The eNodeBs 20 may be connected to each other viaan X2 interface and neighboring eNodeBs may have a meshed networkstructure that has the X2 interface.

As illustrated, eNodeB 20 may perform functions of selection for gateway30, routing toward the gateway during a Radio Resource Control (RRC)activation, scheduling and transmitting of paging messages, schedulingand transmitting of Broadcast Channel (BCCH) information, dynamicallocation of resources to UEs 10 in both uplink and downlink,configuration and provisioning of eNodeB measurements, radio bearercontrol, radio admission control (RAC), and connection mobility controlin LTE_ACTIVE state. In the EPC, and as noted above, gateway 30 mayperform functions of paging origination, LTE-IDLE state management,ciphering of the user plane, System Architecture Evolution (SAE) bearercontrol, and ciphering and integrity protection of Non-Access Stratum(NAS) signaling.

The EPC includes a mobility Management entity (MME), a serving-gateway(S-GW), and a packet data network-gateway (PDN-GW). The MME hasinformation about connections and capabilities of UEs, mainly for use inmanaging the mobility of the UEs. The S-GW is a gateway having theE-UTRAN as an end point, and the PDN-GW is a gateway having a packetdata network (PDN) as an end point.

FIG. 3 is a diagram showing a control plane and a user plane of a radiointerface protocol between a UE and an E-UTRAN based on a 3GPP radioaccess network standard. The control plane refers to a path used fortransmitting control messages used for managing a call between the UEand the E-UTRAN. The user plane refers to a path used for transmittingdata generated in an application layer, e.g., voice data or Internetpacket data.

A physical (PHY) layer of a first layer provides an information transferservice to a higher layer using a physical channel. The PHY layer isconnected to a medium access control (MAC) layer located on the higherlayer via a transport channel. Data is transported between the MAC layerand the PHY layer via the transport channel. Data is transported betweena physical layer of a transmitting side and a physical layer of areceiving side via physical channels. The physical channels use time andfrequency as radio resources. In detail, the physical channel ismodulated using an orthogonal frequency division multiple access (OFDMA)scheme in downlink and is modulated using a single carrier frequencydivision multiple access (SC-FDMA) scheme in uplink.

The MAC layer of a second layer provides a service to a radio linkcontrol (RLC) layer of a higher layer via a logical channel. The RLClayer of the second layer supports reliable data transmission. Afunction of the RLC layer may be implemented by a functional block ofthe MAC layer. A packet data convergence protocol (PDCP) layer of thesecond layer performs a header compression function to reduceunnecessary control information for efficient transmission of anInternet protocol (IP) packet such as an IP version 4 (IPv4) packet oran IP version 6 (IPv6) packet in a radio interface having a relativelysmall bandwidth.

A radio resource control (RRC) layer located at the bottom of a thirdlayer is defined only in the control plane. The RRC layer controlslogical channels, transport channels, and physical channels in relationto configuration, re-configuration, and release of radio bearers (RBs).An RB refers to a service that the second layer provides for datatransmission between the UE and the E-UTRAN. To this end, the RRC layerof the UE and the RRC layer of the E-UTRAN exchange RRC messages witheach other.

One cell of the eNB is set to operate in one of bandwidths such as 1.25,2.5, 5, 10, 15, and 20 MHz and provides a downlink or uplinktransmission service to a plurality of UEs in the bandwidth. Differentcells may be set to provide different bandwidths.

Downlink transport channels for transmission of data from the E-UTRAN tothe UE include a broadcast channel (BCH) for transmission of systeminformation, a paging channel (PCH) for transmission of paging messages,and a downlink shared channel (SCH) for transmission of user traffic orcontrol messages. Traffic or control messages of a downlink multicast orbroadcast service may be transmitted through the downlink SCH and mayalso be transmitted through a separate downlink multicast channel (MCH).

Uplink transport channels for transmission of data from the UE to theE-UTRAN include a random access channel (RACH) for transmission ofinitial control messages and an uplink SCH for transmission of usertraffic or control messages. Logical channels that are defined above thetransport channels and mapped to the transport channels include abroadcast control channel (BCCH), a paging control channel (PCCH), acommon control channel (CCCH), a multicast control channel (MCCH), and amulticast traffic channel (MTCH).

FIG. 4 is a view showing an example of a physical channel structure usedin an E-UMTS system. A physical channel includes several subframes on atime axis and several subcarriers on a frequency axis. Here, onesubframe includes a plurality of symbols on the time axis. One subframeincludes a plurality of resource blocks and one resource block includesa plurality of symbols and a plurality of subcarriers. In addition, eachsubframe may use certain subcarriers of certain symbols (e.g., a firstsymbol) of a subframe for a physical downlink control channel (PDCCH),that is, an L1/L2 control channel. In FIG. 4, an L1/L2 controlinformation transmission area (PDCCH) and a data area (PDSCH) are shown.In one embodiment, a radio frame of 10 ms is used and one radio frameincludes 10 subframes. In addition, one subframe includes twoconsecutive slots. The length of one slot may be 0.5 ms. In addition,one subframe includes a plurality of OFDM symbols and a portion (e.g., afirst symbol) of the plurality of OFDM symbols may be used fortransmitting the L1/L2 control information. A transmission time interval(TTI) which is a unit time for transmitting data is 1 ms.

A base station and a UE mostly transmit/receive data via a PDSCH, whichis a physical channel, using a DL-SCH which is a transmission channel,except a certain control signal or certain service data. Informationindicating to which UE (one or a plurality of UEs) PDSCH data istransmitted and how the UE receive and decode PDSCH data is transmittedin a state of being included in the PDCCH.

For example, in one embodiment, a certain PDCCH is CRC-masked with aradio network temporary identity (RNTI) “A” and information about datais transmitted using a radio resource “B” (e.g., a frequency location)and transmission format information “C” (e.g., a transmission blocksize, modulation, coding information or the like) via a certainsubframe. Then, one or more UEs located in a cell monitor the PDCCHusing its RNTI information. And, a specific UE with RNTI “A” reads thePDCCH and then receive the PDSCH indicated by B and C in the PDCCHinformation.

FIG. 5 is a block diagram of a communication apparatus according to anembodiment of the present invention.

The apparatus shown in FIG. 5 can be a user equipment (UE) and/or eNBadapted to perform the above mechanism, but it can be any apparatus forperforming the same operation.

As shown in FIG. 5, the apparatus may comprises a DSP/microprocessor(110) and RF module (transceiver; 135). The DSP/microprocessor (110) iselectrically connected with the transceiver (135) and controls it. Theapparatus may further include power management module (105), battery(155), display (115), keypad (120), SIM card (125), memory device (130),speaker (145) and input device (150), based on its implementation anddesigner's choice.

Specifically, FIG. 5 may represent a UE comprising a receiver (135)configured to receive a request message from a network, and atransmitter (135) configured to transmit the transmission or receptiontiming information to the network. These receiver and the transmittercan constitute the transceiver (135). The UE further comprises aprocessor (110) connected to the transceiver (135: receiver andtransmitter).

Also, FIG. 5 may represent a network apparatus comprising a transmitter(135) configured to transmit a request message to a UE and a receiver(135) configured to receive the transmission or reception timinginformation from the UE. These transmitter and receiver may constitutethe transceiver (135). The network further comprises a processor (110)connected to the transmitter and the receiver. This processor (110) maybe configured to calculate latency based on the transmission orreception timing information.

Recently, Proximity-based Service (ProSe) has been discussed in 3GPP.The ProSe enables different UEs to be connected (directly) each other(after appropriate procedure(s), such as authentication), through eNBonly (but not further through Serving Gateway (SGW)/Packet Data NetworkGateway (PDN-GW, PGW)), or through SGW/PGW. Thus, using the ProSe,device to device direct communication can be provided, and it isexpected that every devices will be connected with ubiquitousconnectivity. Direct communication between devices in a near distancecan lessen the load of network. Recently, proximity-based social networkservices have come to public attention, and new kinds of proximity-basedapplications can be emerged and may create new business market andrevenue. For the first step, public safety and critical communicationare required in the market. Group communication is also one of keycomponents in the public safety system. Required functionalities are:Discovery based on proximity, Direct path communication, and Managementof group communications.

Use cases and scenarios are for example: i) Commercial/social use, ii)Network offloading, iii) Public Safety, iv) Integration of currentinfrastructure services, to assure the consistency of the userexperience including reachability and mobility aspects, and v) PublicSafety, in case of absence of EUTRAN coverage (subject to regionalregulation and operator policy, and limited to specific public-safetydesignated frequency bands and terminals).

FIG. 6 is an example of default data path for communication between twoUEs. With reference to FIG. 6, even when two UEs (e.g., UE1, UE2) inclose proximity communicate with each other, their data path (userplane) goes via the operator network. Thus a typical data path for thecommunication involves eNB(s) and/or Gateway(s) (GW(s)) (e.g., SGW/PGW).

FIGS. 7 and 8 are examples of data path scenarios for a proximitycommunication. If wireless devices (e.g., UE1, UE2) are in proximity ofeach other, they may be able to use a direct mode data path (FIG. 7) ora locally routed data path (FIG. 8). In the direct mode data path,wireless devices are connected directly each other (after appropriateprocedure(s), such as authentication), without eNB and SGW/PGW. In thelocally routed data path, wireless devices are connected each otherthrough eNB only.

FIG. 9 is a conceptual diagram illustrating for a non-roaming referencearchitecture.

PC1 to PC 5 represent interfaces. PC1 is a reference point between aProSe application in a UE and a ProSe App server. It is used to defineapplication level signaling requirements. PC 2 is a reference pointbetween the ProSe App Server and the ProSe Function. It is used todefine the interaction between ProSe App Server and ProSe functionalityprovided by the 3GPP EPS via ProSe Function. One example may be forapplication data updates for a ProSe database in the ProSe Function.Another example may be data for use by ProSe App Server in interworkingbetween 3GPP functionality and application data, e.g. name translation.PC3 is a reference point between the UE and ProSe Function. It is usedto define the interaction between UE and ProSe Function. An example maybe to use for configuration for ProSe discovery and communication. PC4is a reference point between the EPC and ProSe Function. It is used todefine the interaction between EPC and ProSe Function. Possible usecases may be when setting up a one-to-one communication path between UEsor when validating ProSe services (authorization) for session managementor mobility management in real time.

PC5 is a reference point between UE to UE used for control and userplane for discovery and communication, for relay and one-to-onecommunication (between UEs directly and between UEs over LTE-Uu).Lastly, PC6 is a reference point may be used for functions such as ProSeDiscovery between users subscribed to different PLMNs.

EPC (Evolved Packet Core) includes entities such as MME, S-GW, P-GW,PCRF, HSS etc. The EPC here represents the E-UTRAN Core Networkarchitecture. Interfaces inside the EPC may also be impacted albeit theyare not explicitly shown in FIG. 9.

Application servers, which are users of the ProSe capability forbuilding the application functionality, e.g. in the Public Safety casesthey can be specific agencies (PSAP) or in the commercial cases socialmedia. These applications are defined outside the 3GPP architecture butthere may be reference points towards 3GPP entities. The Applicationserver can communicate towards an application in the UE.

Applications in the UE use the ProSe capability for building theapplication functionality. Example may be for communication betweenmembers of Public Safety groups or for social media application thatrequests to find buddies in proximity. The ProSe Function in the network(as part of EPS) defined by 3GPP has a reference point towards the ProSeApp Server, towards the EPC and the UE.

The functionality may include but not restricted to e.g.:

-   -   Interworking via a reference point towards the 3rd party        Applications    -   Authorization and configuration of the UE for discovery and        Direct communication    -   Enable the functionality of the EPC level ProSe discovery    -   ProSe related new subscriber data and/handling of data storage;        also handling of ProSe identities;    -   Security related functionality    -   Provide Control towards the EPC for policy related functionality    -   Provide functionality for charging (via or outside of EPC, e.g.        offline charging)

Especially, the following identities are used for ProSe DirectCommunication:

-   -   Source Layer-2 ID identifies a sender of a D2D packet at PC5        interface. The Source Layer-2 ID is used for identification of        the receiver RLC UM entity;    -   Destination Layer-2 ID identifies a target of the D2D packet at        PC5 interface. The Destination Layer-2 ID is used for filtering        of packets at the MAC layer. The Destination Layer-2 ID may be a        broadcast, groupcast or unicast identifier; and    -   SA L1 ID identifier in Scheduling Assignment (SA) at PC5        interface. SA L1 ID is used for filtering of packets at the        physical layer. The SA L1 ID may be a broadcast, groupcast or        unicast identifier.

No Access Stratum signaling is required for group formation and toconfigure Source Layer-2 ID and Destination Layer-2 ID in the UE. Thisinformation is provided by higher layers.

In case of groupcast and unicast, the MAC layer will convert the higherlayer ProSe ID (i.e. ProSe Layer-2 Group ID and ProSe UE ID) identifyingthe target (Group, UE) into two bit strings of which one can beforwarded to the physical layer and used as SA L1 ID whereas the otheris used as Destination Layer-2 ID. For broadcast, L2 indicates to L1that it is a broadcast transmission using a pre-defined SA L1 ID in thesame format as for group- and unicast.

FIG. 10 is a conceptual diagram illustrating for a Layer 2 structure forSidelink.

The Sidelink is UE to UE interface for ProSe direct communication andProSe Direct Discovery. Corresponds to the PC5 interface. The Sidelinkcomprises ProSe Direct Discovery and ProSe Direct Communication betweenUEs. The Sidelink uses uplink resources and physical channel structuresimilar to uplink transmissions. However, some changes, noted below, aremade to the physical channels. E-UTRA defines two MAC entities; one inthe UE and one in the E-UTRAN. These MAC entities handle the followingtransport channels additionally, i) sidelink broadcast channel (SL-BCH),ii) sidelink discovery channel (SL-DCH) and iii) sidelink shared channel(SL-SCH).

-   -   Basic transmission scheme: the Sidelink transmission uses the        same basic transmission scheme as the UL transmission scheme.        However, sidelink is limited to single cluster transmissions for        all the sidelink physical channels. Further, sidelink uses a 1        symbol gap at the end of each sidelink sub-frame.    -   Physical-layer processing: the Sidelink physical layer        processing of transport channels differs from UL transmission in        the following steps:

i) Scrambling: for PSDCH and PSCCH, the scrambling is not UE-specific;

ii) Modulation: 64 QAM is not supported for Sidelink.

-   -   Physical Sidelink control channel: PSCCH is mapped to the        Sidelink control resources. PSCCH indicates resource and other        transmission parameters used by a UE for PSSCH.    -   Sidelink reference signals: for PSDCH, PSCCH and PSSCH        demodulation, reference signals similar to uplink demodulation        reference signals are transmitted in the 4th symbol of the slot        in normal CP and in the 3rd symbol of the slot in extended        cyclic prefix. The Sidelink demodulation reference signals        sequence length equals the size (number of subcarriers) of the        assigned resource. For PSDCH and PSCCH, reference signals are        created based on a fixed base sequence, cyclic shift and        orthogonal cover code.    -   Physical channel procedure: for in-coverage operation, the power        spectral density of the sidelink transmissions can be influenced        by the eNB.

FIG. 11a is a conceptual diagram illustrating for User-Plane protocolstack for ProSe Direct Communication, and FIG. 11b is Control-Planeprotocol stack for ProSe Direct Communication.

FIG. 11a shows the protocol stack for the user plane, where PDCP, RLCand MAC sublayers (terminate at the other UE) perform the functionslisted for the user plane (e.g. header compression, HARQretransmissions). The PC5 interface consists of PDCP, RLC, MAC and PHYas shown in FIG. 11 a.

User plane details of ProSe Direct Communication: i) MAC sub headercontains LCIDs (to differentiate multiple logical channels), i) The MACheader comprises a Source Layer-2 ID and a Destination Layer-2 ID, iii)At MAC Multiplexing/demultiplexing, priority handling and padding areuseful for ProSe Direct communication, iv) RLC UM is used for ProSeDirect communication, v) Segmentation and reassembly of RLC SDUs areperformed, vi) A receiving UE needs to maintain at least one RLC UMentity per transmitting peer UE, vii) An RLC UM receiver entity does notneed to be configured prior to reception of the first RLC UM data unit,and viii) U-Mode is used for header compression in PDCP for ProSe DirectCommunication.

FIG. 11b shows the protocol stack for the control plane, where RRC, RLC,MAC, and PHY sublayers (terminate at the other UE) perform the functionslisted for the control plane. A D2D UE does not establish and maintain alogical connection to receiving D2D UEs prior to a D2D communication.

FIG. 12 is a conceptual diagram illustrating for a PC5 interface forProSe Direct Discovery.

ProSe Direct Discovery is defined as the procedure used by theProSe-enabled UE to discover other ProSe-enabled UE(s) in its proximityusing E-UTRA direct radio signals via PC5.

Radio Protocol Stack (AS) for ProSe Direct Discovery is shown in FIG.12.

The AS layer performs the following functions:

-   -   Interfaces with upper layer (ProSe Protocol): The MAC layer        receives the discovery information from the upper layer (ProSe        Protocol). The IP layer is not used for transmitting the        discovery information.    -   Scheduling: The MAC layer determines the radio resource to be        used for announcing the discovery information received from        upper layer.    -   Discovery PDU generation: The MAC layer builds the MAC PDU        carrying the discovery information and sends the MAC PDU to the        physical layer for transmission in the determined radio        resource. No MAC header is added.

There are two types of resource allocation for discovery informationannouncement.

-   -   Type 1: A resource allocation procedure where resources for        announcing of discovery information are allocated on a non UE        specific basis, further characterized by: i) The eNB provides        the UE(s) with the resource pool configuration used for        announcing of discovery information. The configuration may be        signalled in SIB, ii) The UE autonomously selects radio        resource(s) from the indicated resource pool and announce        discovery information, iii) The UE can announce discovery        information on a randomly selected discovery resource during        each discovery period.    -   Type 2: A resource allocation procedure where resources for        announcing of discovery information are allocated on a per UE        specific basis, further characterized by: i) The UE in        RRC_CONNECTED may request resource(s) for announcing of        discovery information from the eNB via RRC, ii) The eNB assigns        resource(s) via RRC, iii) The resources are allocated within the        resource pool that is configured in UEs for monitoring.

For UEs in RRC_IDLE, the eNB may select one of the following options:

-   -   The eNB may provide a Type 1 resource pool for discovery        information announcement in SIB. UEs that are authorized for        Prose Direct Discovery use these resources for announcing        discovery information in RRC_IDLE.    -   The eNB may indicate in SIB that it supports D2D but does not        provide resources for discovery information announcement. UEs        need to enter RRC Connected in order to request D2D resources        for discovery information announcement.

For UEs in RRC_CONNECTED,

-   -   A UE authorized to perform ProSe Direct Discovery announcement        indicates to the eNB that it wants to perform D2D discovery        announcement.    -   The eNB validates whether the UE is authorized for ProSe Direct        Discovery announcement using the UE context received from MME.    -   The eNB may configure the UE to use a Type 1 resource pool or        dedicated Type 2 resources for discovery information        announcement via dedicated RRC signaling (or no resource).    -   The resources allocated by the eNB are valid until a) the eNB        de-configures the resource(s) by RRC signaling or b) the UE        enters IDLE. (FFS whether resources may remain valid even in        IDLE).

Receiving UEs in RRC_IDLE and RRC_CONNECTED monitor both Type 1 and Type2 discovery resource pools as authorized. The eNB provides the resourcepool configuration used for discovery information monitoring in SIB. TheSIB may contain discovery resources used for announcing in neighborcells as well.

FIG. 13 is a conceptual diagram illustrating for overview model of theRLC sub layer.

Functions of the RLC sub layer are performed by RLC entities. For a RLCentity configured at the eNB, there is a peer RLC entity configured atthe UE and vice versa. For an RLC entity configured at the transmittingUE for STCH or SBCCH there is a peer RLC entity configured at eachreceiving UE for STCH or SBCCH.

An RLC entity receives/delivers RLC SDUs from/to upper layer andsends/receives RLC PDUs to/from its peer RLC entity via lower layers. AnRLC PDU can either be a RLC data PDU or a RLC control PDU. If an RLCentity receives RLC SDUs from upper layer, it receives them through asingle SAP between RLC and upper layer, and after forming RLC data PDUsfrom the received RLC SDUs, the RLC entity delivers the RLC data PDUs tolower layer through a single logical channel. If an RLC entity receivesRLC data PDUs from lower layer, it receives them through a singlelogical channel, and after forming RLC SDUs from the received RLC dataPDUs, the RLC entity delivers the RLC SDUs to upper layer through asingle SAP between RLC and upper layer. If an RLC entitydelivers/receives RLC control PDUs to/from lower layer, itdelivers/receives them through the same logical channel itdelivers/receives the RLC data PDUs through.

An RLC entity can be configured to perform data transfer in one of thefollowing three modes: Transparent Mode (TM), Unacknowledged Mode (UM)or Acknowledged Mode (AM). Consequently, an RLC entity is categorized asa TM RLC entity, an UM RLC entity or an AM RLC entity depending on themode of data transfer that the RLC entity is configured to provide.

A TM RLC entity is configured either as a transmitting TM RLC entity ora receiving TM RLC entity. The transmitting TM RLC entity receives RLCSDUs from upper layer and sends RLC PDUs to its peer receiving TM RLCentity via lower layers. The receiving TM RLC entity delivers RLC SDUsto upper layer and receives RLC PDUs from its peer transmitting TM RLCentity via lower layers.

An UM RLC entity is configured either as a transmitting UM RLC entity ora receiving UM RLC entity. The transmitting UM RLC entity receives RLCSDUs from upper layer and sends RLC PDUs to its peer receiving UM RLCentity via lower layers. The receiving UM RLC entity delivers RLC SDUsto upper layer and receives RLC PDUs from its peer transmitting UM RLCentity via lower layers.

An AM RLC entity consists of a transmitting side and a receiving side.The transmitting side of an AM RLC entity receives RLC SDUs from upperlayer and sends RLC PDUs to its peer AM RLC entity via lower layers. Thereceiving side of an AM RLC entity delivers RLC SDUs to upper layer andreceives RLC PDUs from its peer AM RLC entity via lower layers.

The following applies to all RLC entity types (i.e. TM, UM and AM RLCentity): i) RLC SDUs of variable sizes which are byte aligned (i.e.multiple of 8 bits) are supported, and ii) RLC PDUs are formed only whena transmission opportunity has been notified by lower layer (i.e. byMAC) and are then delivered to lower layer.

FIG. 14 is a conceptual diagram illustrating for model of twounacknowledged mode (UM) peer entities.

In UM (Unacknowledged Mode), in-sequence delivery to higher layers isprovided, but no retransmissions of missing PDUs are requested. UM istypically used for services such as VoIP where error-free delivery is ofless importance compared to short delivery time. TM (Transparent Mode),although supported, is only used for specific purposes such as randomaccess.

Unacknowledged mode (UM) supports segmentation/reassembly andin-sequence delivery, but not retransmissions. This mode is used whenerror-free delivery is not required, for example voice-over IP, or whenretransmissions cannot be requested, for example broadcast transmissionson MTCH and MCCH using MBSFN.

When a transmitting UM RLC entity forms UMD PDUs from RLC SDUs, thetransmitting UM RLC entity may i) segment and/or concatenate the RLCSDUs so that the UMD PDUs fit within the total size of RLC PDU(s)indicated by lower layer at the particular transmission opportunitynotified by lower layer; and ii) include relevant RLC headers in the UMDPDU.

When a receiving UM RLC entity receives UMD PDUs, the receiving UM RLCentity may i) detect whether or not the UMD PDUs have been received induplication, and discard duplicated UMD PDUs; ii) reorder the UMD PDUsif they are received out of sequence; iii) detect the loss of UMD PDUsat lower layers and avoid excessive reordering delays; iv) reassembleRLC SDUs from the reordered UMD PDUs (not accounting for RLC PDUs forwhich losses have been detected) and deliver the RLC SDUs to upper layerin ascending order of the RLC SN; and v) discard received UMD PDUs thatcannot be reassembled into a RLC SDU due to loss at lower layers of anUMD PDU which belonged to the particular RLC SDU.

At the time of RLC re-establishment, the receiving UM RLC entity mayreassemble RLC SDUs from the UMD PDUs that are received out of sequenceand deliver them to upper layer, if possible; ii) discard any remainingUMD PDUs that could not be reassembled into RLC SDUs; and iii)initialize relevant state variables and stop relevant timers.

At the time of RLC re-establishment, the receiving UM RLC entity mayreassemble RLC SDUs from the UMD PDUs that are received out of sequenceand deliver them to upper layer, if possible; ii) discard any remainingUMD PDUs that could not be reassembled into RLC SDUs; and iii)initialize relevant state variables and stop relevant timers.

The receiving UM RLC entity may maintain a reordering window accordingto state variable VR(UH) as follows:

i) a SN falls within the reordering window if(VR(UH)−UM_Window_Size)≤SN<VR(UH);

ii) a SN falls outside of the reordering window otherwise.

When receiving an UMD PDU from lower layer, the receiving UM RLC entitymay either discard the received UMD PDU or place it in the receptionbuffer.

If the received UMD PDU was placed in the reception buffer, thereceiving UM RLC may update state variables, reassemble and deliver RLCSDUs to upper layer and start/stop t-Reordering as needed.

When t-Reordering expires, the receiving UM RLC entity may update statevariables, reassemble and deliver RLC SDUs to upper layer and startt-Reordering as needed

When an UMD PDU with SN=x is received from lower layer, the receiving UMRLC entity may discard the received UMD PDU, if VR(UR)<x<VR(UH) and theUMD PDU with SN=x has been received before; or if(VR(UH)−UM_Window_Size)≤x<VR(UR).

Else, the receiving UM RLC entity may place the received UMD PDU in thereception buffer.

When an UMD PDU with SN=x is placed in the reception buffer, thereceiving UM RLC entity may update VR(UH) to x+1 and reassemble RLC SDUsfrom any UMD PDUs with SN that falls outside of the reordering window,remove RLC headers when doing so and deliver the reassembled RLC SDUs toupper layer in ascending order of the RLC SN if not delivered before, ifx falls outside of the reordering window.

If VR(UR) falls outside of the reordering window, the receiving UM RLCentity may set VR(UR) to (VR(UH)−UM_Window_Size).

If the reception buffer contains an UMD PDU with SN=VR(UR), thereceiving UM RLC entity may update VR(UR) to the SN of the first UMD PDUwith SN>current VR(UR) that has not been received; and reassemble RLCSDUs from any UMD PDUs with SN<updated VR(UR), remove RLC headers whendoing so and deliver the reassembled RLC SDUs to upper layer inascending order of the RLC SN if not delivered before;

If t-Reordering is running and VR(UX)≤VR(UR); or if t-Reordering isrunning and VR(UX) falls outside of the reordering window and VR(UX) isnot equal to VR(UH), the receiving UM RLC entity may stop and resett-Reordering.

If t-Reordering is not running (includes the case when t-Reordering isstopped due to actions above) and VR(UH)>VR(UR), the receiving UM RLCentity may start t-Reordering, and set VR(UX) to VR(UH).

When t-Reordering expires, the receiving UM RLC entity may update VR(UR)to the SN of the first UMD PDU with SN≥VR(UX) that has not beenreceived; and reassemble RLC SDUs from any UMD PDUs with SN<updatedVR(UR), remove RLC headers when doing so and deliver the reassembled RLCSDUs to upper layer in ascending order of the RLC SN if not deliveredbefore.

If VR(UH)>VR(UR), the receiving UM RLC entity may start t-Reordering,and set VR(UX) to VR(UH).

Each transmitting UM RLC entity shall maintain the following statevariables above mentioned:

a) VT(US): this state variable holds the value of the SN to be assignedfor the next newly generated UMD PDU. It is initially set to 0, and isupdated whenever the UM RLC entity delivers an UMD PDU with SN=VT(US).

Each receiving UM RLC entity shall maintain the following statevariables above mentioned:

a) VR(UR)−UM receive state variable: this state variable holds the valueof the SN of the earliest UMD PDU that is still considered forreordering. It is initially set to 0.

b) VR(UX)−UM t-Reordering state variable: this state variable holds thevalue of the SN following the SN of the UMD PDU which triggeredt-Reordering.

c) VR(UH)−UM highest received state variable: this state variable holdsthe value of the SN following the SN of the UMD PDU with the highest SNamong received UMD PDUs, and it serves as the higher edge of thereordering window. It is initially set to 0.

FIGS. 15a to 15f are conceptual diagrams illustrating for UMD PDU.

FIG. 15a is a diagram for a UMD PDU with 5 bit SN, FIG. 15b is a diagramfor a UMD PDU with 10 bit SN, FIG. 15c is a diagram for a UMD PDU with 5bit SN (Odd number of LIs, i.e. K=1, 3, 5, . . . ), FIG. 15d is adiagram for a UMD PDU with 5 bit SN (Even number of LIs, i.e. K=2, 4, 6,. . . ), FIG. 15e is a UMD PDU with 10 bit SN (Odd number of LIs, i.e.K=1, 3, 5, . . . ), and FIG. 15f is a diagram for a UMD PDU with 10 bitSN (Even number of LIs, i.e. K=2, 4, 6, . . . ).

An UMD PDU consists of a Data field and an UMD PDU header. UMD PDUheader consists of a fixed part (fields that are present for every UMDPDU) and an extension part (fields that are present for an UMD PDU whennecessary). The fixed part of the UMD PDU header itself is byte alignedand consists of a FI, an E and a SN. The extension part of the UMD PDUheader itself is byte aligned and consists of E(s) and LI(s).

An UM RLC entity is configured by RRC to use either a 5 bit SN or a 10bit SN. When the 5 bit SN is configured, the length of the fixed part ofthe UMD PDU header is one byte. When the 10 bit SN is configured, thefixed part of the UMD PDU header is identical to the fixed part of theAMD PDU header, except for D/C, RF and P fields all being replaced withR1 fields. The extension part of the UMD PDU header is identical to theextension part of the AMD PDU header (regardless of the configured SNsize).

An UMD PDU header consists of an extension part only when more than oneData field elements are present in the UMD PDU, in which case an E and aLI are present for every Data field element except the last.Furthermore, when an UMD PDU header consists of an odd number of LI(s),four padding bits follow after the last LI.

In the definition of each field in FIG. 15a to FIG. 15f , the bits inthe parameters are represented in which the first and most significantbit is the left most bit and the last and least significant bit is therightmost bit. Unless mentioned otherwise, integers are encoded instandard binary encoding for unsigned integers.

-   -   Data field: The Data field elements are mapped to the Data field        in the order which they arrive to the RLC entity at the        transmitter. The granularity of the Data field size is one byte;        and the maximum Data field size is the maximum TB size minus the        sum of minimum MAC PDU header size and minimum RLC PDU header        size. A UMD PDU segment is mapped to the Data field. Zero RLC        SDU segments and one or more RLC SDUs, one or two RLC SDU        segments and zero or more RLC SDUs; the RLC SDU segments are        either mapped to the beginning or the end of the Data field, a        RLC SDU or RLC SDU segment larger than 2047 octets can only be        mapped to the end of the Data field. When there are two RLC SDU        segments, they belong to different RLC SDUs.    -   Sequence number (SN) field: the SN field indicates the sequence        number of the corresponding UMD or AMD PDU. For an AMD PDU        segment, the SN field indicates the sequence number of the        original AMD PDU from which the AMD PDU segment was constructed        from. The sequence number is incremented by one for every UMD or        AMD PDU. Length is 5 bits or 10 bits (configurable) for UMD PDU.    -   Extension bit (E) field: Length is 1 bit. The E field indicates        whether Data field follows or a set of E field and LI field        follows. The interpretation of the E field is provided in Table        1 and Table 2.

TABLE 1 Value Description 0 Data field follows from the octet followingthe fixed part of the header 1 A set of E field and LI field followsfrom the octet following the fixed part of the header

TABLE 2 Value Description 0 Data field follows from the octet followingthe LI field following this E field 1 A set of E field and LI fieldfollows from the bit following the LI field following this E field

-   -   Length Indicator (LI) field: Length is 11 bits. The LI field        indicates the length in bytes of the corresponding Data field        element present in the RLC data PDU delivered/received by an UM        or an AM RLC entity. The first LI present in the RLC data PDU        header corresponds to the first Data field element present in        the Data field of the RLC data PDU, the second LI present in the        RLC data PDU header corresponds to the second Data field element        present in the Data field of the RLC data PDU, and so on. The        value 0 is reserved.    -   Framing Info (FI) field: Length is 2 bits. The FI field        indicates whether a RLC SDU is segmented at the beginning and/or        at the end of the Data field. Specifically, the FI field        indicates whether the first byte of the Data field corresponds        to the first byte of a RLC SDU, and whether the last byte of the        Data field corresponds to the last byte of a RLC SDU. The        interpretation of the FI field is provided in Table 3.

TABLE 3 Value Description 00 First byte of the Data field corresponds tothe first byte of a RLC SDU. Last byte of the Data field corresponds tothe last byte of a RLC SDU. 01 First byte of the Data field correspondsto the first byte of a RLC SDU. Last byte of the Data field does notcorrespond to the last byte of a RLC SDU. 10 First byte of the Datafield does not correspond to the first byte of a RLC SDU. Last byte ofthe Data field corresponds to the last byte of a RLC SDU. 11 First byteof the Data field does not correspond to the first byte of a RLC SDU.Last byte of the Data field does not correspond to the last byte of aRLC SDU.

FIG. 16 is a conceptual diagram for functional view of a PDCP entity.

The PDCP entities are located in the PDCP sublayer. Several PDCPentities may be defined for a UE. Each PDCP entity carrying user planedata may be configured to use header compression. Each PDCP entity iscarrying the data of one radio bearer. In this version of thespecification, only the robust header compression protocol (ROHC), issupported. Every PDCP entity uses at most one ROHC compressor instanceand at most one ROHC decompressor instance. A PDCP entity is associatedeither to the control plane or the user plane depending on which radiobearer it is carrying data for.

FIG. 16 represents the functional view of the PDCP entity for the PDCPsublayer, it should not restrict implementation. For RNs, integrityprotection and verification are also performed for the u-plane.

UL Data Transfer Procedures:

At reception of a PDCP SDU from upper layers, the UE may start a discardtimer associated with the PDCP SDU. For a PDCP SDU received from upperlayers, the UE may associate a PDCP SN (Sequence Number) correspondingto Next_PDCP_TX_SN to the PDCP SDU, perform header compression of thePDCP SDU, perform integrity protection and ciphering using COUNT basedon TX_HFN and the PDCP SN associated with this PDCP SDU, increment theNext_PDCP_TX_SN by one, and submit the resulting PDCP Data PDU to lowerlayer.

If the Next_PDCP_TX_SN is greater than Maximum_PDCP_SN, theNext_PDCP_TX_SN is set to ‘0’ and TX_HFN is incremented by one.

DL Data Transfer Procedures:

For DRBs mapped on RLC UM, at reception of a PDCP Data PDU from lowerlayers, if received PDCP SN<Next_PDCP_RX_SN, the UE may increment RX_HFNby one, and decipher the PDCP Data PDU using COUNT based on RX_HFN andthe received PDCP SN. And the UE may set Next_PDCP_RX_SN to the receivedPDCP SN+1. If Next_PDCP_RX_SN>Maximum_PDCP_SN, the UE may setNext_PDCP_RX_SN to 0, and increment RX_HFN by one.

The UE may perform header decompression (if configured) of thedeciphered PDCP Data PDU, and deliver the resulting PDCP SDU to upperlayer.

FIG. 17 is a conceptual diagram for transmitting aRadioResourceConfigDedicated from E-UTRAN to a UE.

The UE may release a PDCP entity, a RLC entity(s), a DTCH logicalchannel or drb-identity according to the RadioResourceConfigDedicatedmessage, for each drb-Identity value included in the drb-ToAddModListthat is part of the current UE configuration.

For each drb-Identity value included in the drb-ToReleaseList that ispart of the current UE configuration (DRB release), or for eachdrb-identity value that is to be released as the result of fullconfiguration option, the UE may release the PDCP entity, the RLCentity(s), or the DTCH logical channel.

The IE RadioResourceConfigDedicated is used to setup/modify/release RBs,to modify the MAC main configuration, to modify the SPS configurationand to modify dedicated physical configuration.

The IE RadioResourceConfigDedicated includes the drb-ToAddModListincluding pdcp-Config and rlc-Config, such as following Table 1.

TABLE 1 RadioResourceConfigDedicated• information• element 

--•ASN1START 

 

RadioResourceConfigDedicated•::= → → SEQUENCE•{ 

→ srb-ToAddModList → → → → → SRB-ToAddModList → → → OPTIONAL,•→ →--•Cond•HO-Conn 

→ drb-ToAddModList → → → → → DRB-ToAddModList → → → OPTIONAL,•→ →--•Cond•HO- ... SRB-ToAddModList•::= → → → →SEQUENCE•(SIZE•(1..2))•OF•SRB-ToAddMod 

SRB-ToAddMod•::= → SEQUENCE•{ 

→ srb-Identity → → → → → → INTEGER•(1..2), 

→ rlc-Config→ → → → → → → CHOICE•{ 

→ → explicitValue → → → → → → RLC-Config, 

→ → defaultValue → → → → → → NULL 

→ } → → OPTIONAL, → → → → → → → → → → → → → → → → --•Cond•Setup 

→ logicalChannelConfig → → → → CHOICE•{ 

→ → explicitValue → → → → → → LogicalChannelConfig, 

→ → defaultValue → → → → → → NULL 

→ } → → OPTIONAL, → → → → → → → → → → → → → → → → --•Cond•Setup 

→ ... 

} 

DRB-ToAddModList•::= → → → →SEQUENCE•(SIZE•(1..maxDRB))•OF•DRB-ToAddMod 

DRB-ToAddMod•::= → SEQUENCE•{ 

→ eps-BearerIdentity→ → → → → INTEGER•(0..15)→ → → OPTIONAL, → →--•Cond•DRB-Setup 

→ drb-Identity → → → → → → DRB-Identity, 

→ pdcp-Config→ → → → → → → PDCP-Config→ → → → OPTIONAL, → →--•Cond•PDCP 

→ rlc-Config→ → → → → → → RLC-Config→ → → → OPTIONAL, → → --•Cond•Setup 

→ logicalChannelIdentity→ → → → INTEGER•(3..10)→ → → OPTIONAL, → →--•Cond•DRB-Setup 

→ logicalChannelConfig → → → → LogicalChannelConfig → OPTIONAL, → →--•Cond•Setup 

→ ... 

} 

DRB-ToReleaseList•::=→ → → →SEQUENCE•(SIZE•(1..maxDRB))•OF•DRB-Identity 

The DRB-ToReleaseList includes sequence (size (1 . . . maxDRB)) ofDRB-Identity. The parameter of maxDRB indicates maximum number of DataRadio Bearers.

In order to release L2 entities such as an RLC entity and a PDCP entity,a UE needs to be sure that there would be no more D2D datacommunication. For this, in the legacy system, the UE receives an RRCmessage (i.e., DRB-ToReleaseList information element inRadioResourceConfigDedicated) when a radio bearer is released by an eNB.The RRC message includes the identity of radio bearer to be released.Accordingly, the UE releases the L2 entities for the corresponding radiobearer.

In D2D communication, a transmitting UE (txUE) is identified bysourceID, a receiving UE is identified by targetID, and the logicalchannel is identified by LCID.

The layer2 (L2) entities such as a RLC entity and a PDCP entity areestablished per sidelink radio bearer (D2D-RB). In other words, the L2entities are established for each [targetID, sourceID, LCID]combination. When the rxUE establishes the L2 entities, theconfiguration parameters are received from either the network or thetxUE, including PDCP-SN-Size, headerCompression, SN-FieldLength, andT-Reordering. When the rxUE receives D2D packet, the rxUE deliver D2Dpacket to upper layer based on targetID, sourceID, and LCID. As long asthe targetID, sourceID, and LCID are valid and L2 entities areestablished with correct configuration parameters, D2D packets will besuccessfully decoded.

However, there would be a case continuous L2 configuration error occurseven though the rxUE receives a D2D data with a valid targetID,sourceID, and LCID. This implies that the L2 entities are notestablished correctly: at least one of the L2 configuration parametersis not correctly received by the rxUE because the L2 configurationparameters are possible delivered by L2 signal. In this case, continuouserror cannot be avoided if the L2 entities are released and newlyestablished for the D2D-RB.

FIG. 18 is a conceptual diagram for a configuration error management fora sidelink radio bearer according to embodiments of the presentinvention.

In D2D communication, it is invented that the rxUE detects L2CONfiguration ERror (L2 CONER) for a sidelink radio bearer (D2D-RB)based on erroneous D2D packets in corresponding RLC and/or PDCPentities. The txUE and rxUE establishes an RLC entity and a PDCP entityper a D2D-RB. A txUE is identified by Source Layer-2 ID (sourceID) andan rxUE is identified by Destination Layer-2 ID (targetID). A logicalchannel is identified by LCID.

Upon detecting L2 CONER of the D2D-RB, the rxUE may transmit the L2CONER Report for the D2D-RB to the network or the txUE (A). Or, the rxUEmay release a RLC and a PDCP entities for the D2D-RB (B). Additionally,the rxUE may transmit a configuration error recovery request to thenetwork or the txUE and the network or txUE transmits L2 configurationinformation to rxUE for D2D-RB recovery (C).

FIG. 19 is a conceptual diagram for a configuration error management fora sidelink radio bearer according to embodiments of the presentinvention.

When the rxUE receives one or more D2D packets via a D2D-RB (S1901), theUE counts erroneous D2D packets among the one or more D2D packets(S1903).

Preferably, the rxUE considers that the received D2D packet has the L2CONER in the following cases: i) header decompression failure occurs inPDCP entity of the D2D-RB, ii) a PDCP PDU that contains reserved orinvalid values is received in PDCP entity of the D2D-RB, or iii) a RLCPDU that contains reserved or invalid values is received in RLC entityof the D2D-RB.

The rxUE detects L2 CONER for the D2D-RB if the number of the countederroneous D2D packets is equal to or larger than a threshold (S1905). Ifnot, the rxUE doesn't consider the D2D-RB as the L2 CONER (S1907).

Preferably, for the D2D-RB, the rxUE detects the L2 CONER when the rxUEreceives: i) a pre-defined number of erroneous D2D packets of theD2D-RB; or ii) a pre-defined number of consecutive erroneous D2D packetsof the D2D-RB; or iii) a pre-defined number of erroneous D2D packets ofthe D2D-RB within a pre-defined time period; or iv) a pre-defined numberof consecutive erroneous D2D packets of the D2D-RB within a pre-definedtime period.

Preferably, the erroneous D2D packets are counted in only a RLC entity,only a PDCP entity or both of the RLC entity and the PDCP entity.

The number of erroneous D2D packets, the number of consecutive erroneousD2D packets, or the time period used for L2 CONER detection isconfigured by the network or the txUE. The network or the txUE transmitsa separate value for each D2D-RB; or the network or the txUE transmits acommon value for all D2D-RBs.

The network or the txUE transmits to the rxUE the value via at least oneof an RRC (Radio Resource Control), PDCP (Packet Data ConvergenceProtocol), RLC (Radio Link Control), MAC (Medium Access Control), or PHY(PHYsical) signal.

The number of erroneous D2D packets, the number of consecutive erroneousD2D packets, or the time period used for L2 CONER detection ispre-defined in the specification. A separate value is pre-defined foreach D2D-RB; or a common value is pre-defined for all D2D-RBs.

When the rxUE detects the L2 CONER for the D2D-RB, the rxUE generatesconfiguration error report (L2 CONER Report) for the D2D-RB (S1909). Andthe rxUE transmits the L2 CONER Report to a network or a peer UEdirectly connected to the UE via a sidelink (S1911).

Preferably, the L2 CONER Report includes at least one of i) Identifierof the D2D-RB of detected L2 CONER, e.g., SourceID, TargetID, LCID, ii)Location of detected L2 CONER, e.g., PDCP or RLC; or iii) Type ofdetected L2 CONER, e.g., header decompression, reception of a PDCP PDUcontaining reserved or invalid values, or reception of a RLC PDUcontaining reserved or invalid values.

Preferably, the L2 CONER Report is transmitted via at least one of anRRC, PDCP, RLC, MAC, or PHY signal.

Preferably, the rxUE may transmit the L2 CONER Report one or more timesto the network or the txUE. The number of transmission is configured bythe network or the txUE, or pre-defined in the specification.

When the rxUE transmits L2 CONER Report for the D2D-RB to the network orto the txUE, the rxUE may release L2 entities for the D2D-RB (S1913).

FIG. 20 is a conceptual diagram for a configuration error management fora sidelink radio bearer according to embodiments of the presentinvention.

When the rxUE receives one or more D2D packets via a D2D-RB (S2001), theUE counts erroneous D2D packets among the one or more D2D packets(S2003).

Preferably, the rxUE considers that the received D2D packet has the L2CONER in the following cases: i) header decompression failure occurs inPDCP entity of the D2D-RB, ii) a PDCP PDU that contains reserved orinvalid values is received in PDCP entity of the D2D-RB, or iii) a RLCPDU that contains reserved or invalid values is received in RLC entityof the D2D-RB.

The rxUE detects L2 CONER for the D2D-RB if the number of the countederroneous D2D packets is equal to or larger than a threshold (S2005). Ifnot, the rxUE doesn't consider the D2D-RB as the L2 CONER (S2007).

Preferably, for the D2D-RB, the rxUE detects the L2 CONER when the rxUEreceives: i) a pre-defined number of erroneous D2D packets of theD2D-RB; or ii) a pre-defined number of consecutive erroneous D2D packetsof the D2D-RB; or iii) a pre-defined number of erroneous D2D packets ofthe D2D-RB within a pre-defined time period; or iv) a pre-defined numberof consecutive erroneous D2D packets of the D2D-RB within a pre-definedtime period.

Preferably, the erroneous D2D packets are counted in only a RLC entity,only a PDCP entity or both of the RLC entity and the PDCP entity.

The number of erroneous D2D packets, the number of consecutive erroneousD2D packets, or the time period used for L2 CONER detection isconfigured by the network or the txUE. The network or the txUE transmitsa separate value for each D2D-RB; or the network or the txUE transmits acommon value for all D2D-RBs.

The network or the txUE transmits to the rxUE the value via at least oneof an RRC, PDCP, RLC, MAC, or PHY signal.

The number of erroneous D2D packets, the number of consecutive erroneousD2D packets, or the time period used for L2 CONER detection ispre-defined in the specification. A separate value is pre-defined foreach D2D-RB; or a common value is pre-defined for all D2D-RBs.

When the rxUE detects the L2 CONER for the D2D-RB, the rxUE may releaseL2 entities for the D2D-RB (S2009).

FIG. 21 is a conceptual diagram for a configuration error management fora sidelink radio bearer according to embodiments of the presentinvention.

When the rxUE receives one or more D2D packets via a D2D-RB (S2101), theUE counts erroneous D2D packets among the one or more D2D packets(S2103).

Preferably, the rxUE considers that the received D2D packet has the L2CONER in the following cases: i) header decompression failure occurs inPDCP entity of the D2D-RB, ii) a PDCP PDU that contains reserved orinvalid values is received in PDCP entity of the D2D-RB, or iii) a RLCPDU that contains reserved or invalid values is received in RLC entityof the D2D-RB.

The rxUE detects L2 CONER for the D2D-RB if the number of the countederroneous D2D packets is equal to or larger than a threshold (S2105). Ifnot, the rxUE doesn't consider the D2D-RB as the L2 CONER (S2107).

Preferably, for the D2D-RB, the rxUE detects the L2 CONER when the rxUEreceives: i) a pre-defined number of erroneous D2D packets of theD2D-RB; or ii) a pre-defined number of consecutive erroneous D2D packetsof the D2D-RB; or iii) a pre-defined number of erroneous D2D packets ofthe D2D-RB within a pre-defined time period; or iv) a pre-defined numberof consecutive erroneous D2D packets of the D2D-RB within a pre-definedtime period.

Preferably, the erroneous D2D packets are counted in only a RLC entity,only a PDCP entity or both of the RLC entity and the PDCP entity.

The number of erroneous D2D packets, the number of consecutive erroneousD2D packets, or the time period used for L2 CONER detection isconfigured by the network or the txUE. The network or the txUE transmitsa separate value for each D2D-RB; or the network or the txUE transmits acommon value for all D2D-RBs.

The network or the txUE transmits to the rxUE the value via at least oneof an RRC, PDCP, RLC, MAC, or PHY signal.

The number of erroneous D2D packets, the number of consecutive erroneousD2D packets, or the time period used for L2 CONER detection ispre-defined in the specification. A separate value is pre-defined foreach D2D-RB; or a common value is pre-defined for all D2D-RBs.

When the rxUE detects the L2 CONER for the D2D-RB, the rxUE may start atimer (L2 RecoveryTimer) (S2109) and generates a configuration errorrecovery request (L2 RecoveryRequest) (S2111).

Preferably, the rxUE maintains the L2 RecoveryTimer per D2D-RB and therxUE maintains the L2 RecoveryTimer in a RRC, a PDCP, a RLC, a MAC, aPHY layer.

Preferably, the L2 RecoveryTimer is configured by the network or thetxUE, i) the network the txUE transmits a separate value for eachD2D-RB; or ii) the network the txUE transmits a separate value a commonvalue for all D2D-RBs. The network or the txUE transmits to the rxUE thevalue of the L2 RecoveryTimer via RRC/PDCP/RLC/MAC/PHY signal.

Preferably, the L2 RecoveryTimer is specified in the specification. Aseparate value is pre-defined for each D2D-RB; or a separate value ispre-defined for all D2D-RBs.

The rxUE transmits the L2 RecoveryRequest to a network or a peer UEdirectly connected to the UE via a sidelink (S2113).

Preferably, the L2 RecoveryRequest includes at least one of i)identifier of the D2D-RB of detected L2 CONER, e.g., SourceID, TargetID,LCID; or ii) location of detected L2 CONER, e.g., PDCP or RLC; or iii)type of detected L2 CONER, e.g., header decompression, reception of aPDCP PDU containing reserved or invalid values, or reception of a RLCPDU containing reserved or invalid values.

Preferably, the rxUE transmits L2 RecoveryRequest to the network or thetxUE by using at least one of an RRC, PDCP, RLC, MAC, or PHY signal.

Meanwhile, when the network or the txUE receives L2 RecoveryRequest fromthe rxUE, i) the network or the txUE checks the identifier of theD2D-RB; or ii) the network or the txUE checks the location of the L2CONER; or iii) the network or the txUE checks the type of the L2 CONER;or iv) the network or the txUE considers that the RLC and PDCP entitiesof the indicated D2D-RB are configured with invalid configurationparameters. The network or the txUE transmits L2 configurationinformation for the indicated D2D-RB by using at least one of an RRC,PDCP, RLC, MAC, or PHY signal.

When the rxUE receives L2 configuration information for the D2D-RB fromthe network or the txUE (S2115), the rxUE stops the L2 RecoveryTimer ofthe D2D-RB (S2117), and establishes or re-establishes L2 entities of theD2D-RB according to the received L2 configuration information (S2119).

Preferably, the L2 configuration information includes at least one ofPDCP-SN-Size, headerCompression, SN-FieldLength, and T-Reordering.

When the L2 RecoveryTimer expires for the D2D-RB, the rx UE considers L2recovery fails for the D2D-RB, and may transmit L2 RecoveryFailindicator to the network or the txUE (S2121).

Preferably, the L2 RecoveryFail indicator includes an identifier of thesidelink radio bearer including at least one of a SourceID, a TargetIDor a LCID.

Preferably, the rxUE transmits the L2 RecoveryFail indicator by using atleast one of an RRC, PDCP, RLC, MAC, or PHY signal.

The rxUE releases the RLC and the PDCP entities of the sidelink radiobearer after the recovery fail indicator is transmitted (S2113).

The embodiments of the present invention described hereinbelow arecombinations of elements and features of the present invention. Theelements or features may be considered selective unless otherwisementioned. Each element or feature may be practiced without beingcombined with other elements or features. Further, an embodiment of thepresent invention may be constructed by combining parts of the elementsand/or features. Operation orders described in embodiments of thepresent invention may be rearranged. Some constructions of any oneembodiment may be included in another embodiment and may be replacedwith corresponding constructions of another embodiment. It is obvious tothose skilled in the art that claims that are not explicitly cited ineach other in the appended claims may be presented in combination as anembodiment of the present invention or included as a new claim bysubsequent amendment after the application is filed.

In the embodiments of the present invention, a specific operationdescribed as performed by the BS may be performed by an upper node ofthe BS. Namely, it is apparent that, in a network comprised of aplurality of network nodes including a BS, various operations performedfor communication with an MS may be performed by the BS, or networknodes other than the BS. The term ‘eNB’ may be replaced with the term‘fixed station’, ‘Node B’, ‘Base Station (BS)’, ‘access point’, etc.

The above-described embodiments may be implemented by various means, forexample, by hardware, firmware, software, or a combination thereof.

In a hardware configuration, the method according to the embodiments ofthe present invention may be implemented by one or more ApplicationSpecific Integrated Circuits (ASICs), Digital Signal Processors (DSPs),Digital Signal Processing Devices (DSPDs), Programmable Logic Devices(PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers,microcontrollers, or microprocessors.

In a firmware or software configuration, the method according to theembodiments of the present invention may be implemented in the form ofmodules, procedures, functions, etc. performing the above-describedfunctions or operations. Software code may be stored in a memory unitand executed by a processor. The memory unit may be located at theinterior or exterior of the processor and may transmit and receive datato and from the processor via various known means.

Those skilled in the art will appreciate that the present invention maybe carried out in other specific ways than those set forth hereinwithout departing from the spirit and essential characteristics of thepresent invention. The above embodiments are therefore to be construedin all aspects as illustrative and not restrictive. The scope of theinvention should be determined by the appended claims and their legalequivalents, not by the above description, and all changes coming withinthe meaning and equivalency range of the appended claims are intended tobe embraced therein.

INDUSTRIAL APPLICABILITY

While the above-described method has been described centering on anexample applied to the 3GPP LTE system, the present invention isapplicable to a variety of wireless communication systems in addition tothe 3GPP LTE system.

The invention claimed is:
 1. A method for a User Equipment (UE)operating in a wireless communication system, the method comprising:detecting a configuration error for a sidelink radio bearer comprising aRadio Link Control (RLC) entity and a Packet Data Convergence Protocol(PDCP) entity; starting a timer when the configuration error for thesidelink radio bearer is detected; generating a configuration errorrecovery request including an identifier of the sidelink radio bearer;and transmitting the configuration error recovery request to a networkor a peer UE directly connected to the UE via a sidelink, wherein theconfiguration error for the sidelink radio bearer is detected when anumber of erroneous Device to Device (D2D) packets is equal to or largerthan a threshold, and wherein the erroneous D2D packets are countedamong D2D packets received via the sidelink radio bearer.
 2. The methodaccording to claim 1, wherein the identifier of the sidelink radiobearer includes at least one of a Source identifier (ID), a Target ID ora Logical Channel ID (LCID).
 3. The method according to claim 1, whereinthe configuration error recovery request further comprises layerinformation of the detected configuration error, or type information ofthe detected configuration error.
 4. The method according to claim 3,wherein the type information of the detected configuration errorincludes at least one of a header decompression, reception of a PDCPProtocol Data Unit (PDU) containing reserved or invalid values, orreception of a RLC PDU containing reserved or invalid values.
 5. Themethod according to claim 1, further comprising: receiving configurationinformation in response to the configuration error recovery request fromthe peer UE or the network while the timer is running; stopping thetimer when the configuration information is received; andre-establishing the RLC entity and the PDCP entity for the sidelinkradio bearer according to the configuration information.
 6. The methodaccording to claim 5, wherein the configuration information includes atleast one of a PDCP-Sequence Number (SN)-Size, headerCompression,SN-FieldLength, and T-Reordering.
 7. The method according to claim 1,further comprising: transmitting a recovery fail indicator to thenetwork or to the peer UE when the timer expires.
 8. The methodaccording to claim 7, wherein the recovery fail indicator includes anidentifier of the sidelink radio bearer including at least one of aSource identifier (ID), a Target ID or a LCID Logical Channel ID (LCID).9. The method according to claim 7, further comprising: releasing theRLC entity and the PDCP entity of the sidelink radio bearer after therecovery fail indicator is transmitted.
 10. The method according toclaim 1, wherein a value of the timer is received from the network orthe peer UE in a form of at least one of Radio Resource Control (RRC),PDCP, RLC, Medium Access Control (MAC), or PHYsical (PHY) signal, or thevalue of the timer is predefined.
 11. The method according to claim 1,wherein the timer is configured per the sidelink radio bearer, wherein avalue of the timer has an independent value used for each of a pluralityof timers, or wherein a value of the timer has a common value used forall of the plurality of timers.
 12. The method according to claim 1,wherein the UE counts only consecutive erroneous D2D packets when theerroneous D2D packets are counted.
 13. The method according to claim 1,wherein the counted erroneous D2D packets are received consecutivelywhen the configuration error is detected.
 14. The method according toclaim 1, wherein the counted erroneous D2D packets are received within apredefined time period.
 15. The method according to claim 1, wherein theD2D packets are counted as the erroneous D2D packets in one of followingcases: when header decompression failure occurs in the PDCP entity ofthe sidelink radio bearer; when a PDCP Protocol Data Unit (PDU) thatcontains reserved or invalid values is received in the PDCP entity ofthe sidelink radio bearer; or when a RLC PDU that contains reserved orinvalid values is received in a RLC entity of the sidelink radio bearer.16. A User Equipment (UE) for operating in a wireless communicationsystem, the UE comprising: a Radio Frequency (RF) transceiver; and aprocessor operably coupled with the RF transceiver and configured to:detect a configuration error for a sidelink radio bearer comprising aRadio Link Control (RLC) entity and a Packet Data Convergence Protocol(PDCP) entity; start a timer when the configuration error for thesidelink radio bearer is detected; generate a configuration errorrecovery request including an identifier of the sidelink radio bearer;and transmit, using the RF transceiver, the configuration error recoveryrequest to a network or a peer UE directly connected to the UE via asidelink, wherein the configuration error for the sidelink radio beareris detected when a number of erroneous Device to Device (D2D) packets isequal to or larger than a threshold, and wherein the erroneous D2Dpackets are counted among D2D packets received via the sidelink radiobearer.
 17. The UE according to claim 16, wherein the processor isfurther configured to: receive configuration information in response tothe configuration error recovery request from the peer UE or the networkwhile the timer is running; stop the timer when the configurationinformation is received; and re-establish the RLC entity and the PDCPentity for the sidelink radio bearer according to the configurationinformation.
 18. The UE according to claim 16, wherein the processor isfurther configured to: transmit a recovery fail indicator to the networkor to the peer UE when the timer expires.
 19. The UE according to claim18, wherein the processor is further configured to: release the RLCentity and the PDCP entity of the sidelink radio bearer after therecovery fail indicator is transmitted.